Skip to main content
Check and provide your planning data

BETA This is a new service – your feedback will help us to improve it.

Back to dataset table
East Hampshire District Council

Tree

There is a problem

  • 1000 entries with tree-preservation-order field must match the reference field in the tree preservation order

1647

reference
594-tree-1
name
1647
tree-preservation-order

undefined

594-tpo-1
uprn
address-text
point
POINT (-1.019591 50.882181)
geometry
MULTIPOLYGON (((-1.019520 50.882173,-1.019523 50.882187,-1.019533 50.882200,-1.019549 50.882210,-1.019568 50.882216,-1.019590 50.882219,-1.019612 50.882217,-1.019632 50.882210,-1.019648 50.882201,-1.019658 50.882188,-1.019662 50.882174,-1.019659 50.882160,-1.019649 50.882148,-1.019634 50.882138,-1.019614 50.882131,-1.019592 50.882129,-1.019570 50.882131,-1.019550 50.882137,-1.019534 50.882147,-1.019524 50.882159,-1.019520 50.882173)))
notes
felled-date
entry-date
2026-08-06
start-date
end-date

How to fix this issue

Your data is missing a tree-preservation-order.

The tree guidance explains how to fix the issue:

tree-preservation-order

The reference for the tree preservation order that affects this tree.

Example: TPO1

This diagram shows the relationship between the tree preservation order dataset and the tree dataset. The reference value from your tree preservation order dataset needs to match the tree-preservation-order value in your tree dataset.

How to improve East Hampshire District Council’s data

  1. Fix the errors indicated
  2. Use the check service to make sure the data meets the standard
  3. Publish the updated data on the endpoint URL